docs(types): finish the ObjectTable -> ObjectGrid rename in two stale doc comments - #2947
Merged
Conversation
… doc comments Follow-up to #2938. `ObjectTable` is not a typo but a historical artifact: the component was renamed to `ObjectGrid` long ago (see the "ObjectTable: Auto-generates tables from ObjectQL object schemas" entries still recorded in the package CHANGELOGs), and some prose never followed. #2938 fixed the one occurrence that actually bit authors — the `kind:'react'` page scope comment, where the prose *is* the API documentation for a runtime-derived scope. These two are lower-stakes descriptive prose on type definitions, cleaned up so the dead name stops surviving in live code: - field-types.ts — the module doc for the field type system. - objectql.ts — `ObjectViewSchema`. Factually correct as well as mechanical: ObjectView renders an `object-grid` (plugin-view/src/ObjectView.tsx:858). `ObjectTable` now appears only in the package CHANGELOGs (immutable history), gitignored `dist/` output, and sdui-parser's synthetic compiler fixtures. Comment-only; no behavior change. Co-Authored-By: Claude <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
Contributor
✅ Console Performance Budget
📦 Bundle Size Report
Size Limits
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #2938.
Context
While fixing #2938 I traced where
ObjectTablecame from. It is not a typo —the component genuinely existed and was renamed to
ObjectGridlong ago. Theoriginal still sits in the package CHANGELOGs:
Some prose never followed the rename.
Why this PR is small
#2938 fixed the one occurrence that actually bit authors: the
kind:'react'page scope comment, where the prose is the API documentation for a scope that
is derived at runtime, so following it produced a
ReferenceError.These two are lower-stakes descriptive prose on type definitions — nobody
writes
<ObjectTable>because of them. The value is retiring a dead name fromlive code so the next reader doesn't go digging.
Changes
field-types.ts:15objectql.ts:1230ObjectViewSchema— factually correct, not just mechanical: ObjectView renders anobject-grid(plugin-view/src/ObjectView.tsx:858)After this
ObjectTableappears only in:dist/output — regenerates,sdui-parsersynthetic compiler fixtures — these build their own inlinemanifests and never touch the real registry.
Not done deliberately
I considered a test pinning
PUBLIC_BLOCKSagainst actually-registered types tostop this class of drift, and decided against it: "a component not yet registered
is simply skipped (the list is aspirational-safe)"
(public-blocks.ts:20) is
intentional design, since plugin packages may not be loaded. A hard assertion
would fight that.
Comment-only — no behavior change, no changeset (not a feature).
🤖 Generated with Claude Code